When you configure a cluster, identify the possible failures that can interrupt access to resources. A single point of failure is any component in your environment that would block data or applications if it failed. Single points of failure can be hardware, software, or external dependencies, such as power supplied by a utility company and dedicated wide area network (WAN) lines.
In general, you provide maximum reliability when you:
With
The following table lists common points of failure and describes whether the point of failure can be protected, either by server clusters or by other means.
Failure point | Server cluster solution | Other solutions |
---|---|---|
Network hub | Redundant networks. For more information, see Configuring cluster network hardware. | — |
Utility company power | — | Uninterruptible power supply (UPS).
Put each cluster node on a separate circuit. |
Server connection | Failover | — |
Disk | — | Hardware RAID, to protect the data on the disk. For more information, see Hardware redundant array of independent disks (RAID). |
Other server hardware, such as CPU or memory. | Failover | — |
Server software, such as the operating system or specific applications. | Failover | — |
Wide area network (WAN) links, such as routers and dedicated lines. | — | Redundant links over the WAN, to provide secondary access to remote connections. |
Dial-up connection | — | Multiple modems. |
Client computer within your organization | — | Configuring multiple clients for the same level of access. If one client fails, you still have access through other clients. |
Authentication of the cluster service account | — | Redundant networks.
Configure individual nodes as domain controllers. |
To further increase the availability of network resources and prevent the loss of data: